Aborting a mirror transfer

You can abort a volume replication operation before the data transfer is complete. You can abort a scheduled update, a manual update, or an initial data transfer.

Steps

1.	From the home page, double-click the appropriate storage system.

2.	Expand the Storage Virtual Machines hierarchy in the left navigation pane.

3.	In the navigation pane, select the Storage Virtual Machine (SVM) that contains the destination volume and click Protection.

4.	Select the relationship for which you want to stop the data transfer, and click Operations > Abort.

5.	Select Yes, I want to abort the transfer to confirm the operation.

6.	Select Keep any partially transferred data to retain the data that is already transferred to the destination volume.

7.	Click Abort.

8.	If you are aborting data transfers on an Infinite Volume, click Run in Background to run the operation in the background.

It takes longer to abort data transfers of Infinite Volumes than of a FlexVol volume.

Result

The Transfer Status is displayed as Aborting until the operation is complete. After the operation is complete, the Transfer Status is displayed as Idle.

Related reference

Protection window

Upgrading older style data protection mirror relationships

Data protection mirror relationships that you have before upgrading to Data ONTAP 8.2 use a different relationship syntax and are not upgraded when you upgrade Data ONTAP. You must upgrade the Data ONTAP 8.1.x relationship syntax style to the Data ONTAP 8.2 and later syntax style if you want to use new features and improvements.

About this task

After you upgrade a cluster, the cluster is fully operational with no disruption to existing services. However, data protection mirror relationships will not be able to take advantage of the new release's features because changing the syntax of the data protection mirror relationships from Data ONTAP 8.1.x syntax to Data ONTAP 8.2 and later syntax is not included in the upgrade.

Note: If you have data protection mirror relationships that span cluster peers, you must upgrade both destination and source clusters to clustered Data ONTAP 8.2 before upgrading older style data protection mirror relationships.

With Data ONTAP 8.2.1, conversion of data protection mirror relationships from the 8.1.x style to the 8.2 and later style is initiated when you create a Storage Virtual Machine (SVM) peer relationship.

To take advantage of the new features, you must create an SVM peer relationship. Creating an SVM peer relationship automatically initiates the conversion of Data ONTAP 8.1.x style data protection mirror relationships to Data ONTAP 8.2 style data protection mirror relationships.

SVM peering requires unique SVM names. You should name SVMs with a unique fully qualified domain name (FQDN), for example, "dataVerser.HQ" or "mirrorVserver.Offsite". Using the FQDN naming style makes it much easier to make sure of uniqueness.

Steps

1.	Show the relationship-capability of the data protection mirror relationships by using the snapmirror show command with the -fields relationship-capability parameter.

2.	Create SVM peer relationships:

a.	On one of the clusters of the cluster peer relationship, create SVM peer relationships by using the vserver peer create command.

If you have more than one SnapMirror relationship that uses the same two SVMs, then you need to create only one SVM peer relationship.

b.	On the other cluster of the cluster peer relationship, accept the SVM create request by using the vserver peer accept command.

c.	If there is a name conflict, change the name of one of the SVMs by using the vserver rename command.

In addition to creating the SVM peer relationship, Data ONTAP upgrades the data protection mirror relationships to Data ONTAP 8.2 style relationships.

Note: Load-sharing mirror relationships cannot be upgraded to the Data ONTAP 8.2 style. The "Relationship capability" field of the detailed view of the snapmirror show command will show as "Pre 8.2".

3.	Ensure that all of the data protection mirror relationships are displayed as healthy and have relationship-capability of 8.2 and above by using the snapmirror show command with the -instances parameter.